Chapter 3-10: Inquiry Processes |
Inquiry Process Additional Attributes Option The Additional Attributesoption accesses the Inquiry Process Additional Attributes overlay, shown below, from which you can alter the standard EM attributes.
Inquiry Process Additional Attributes Overlay The Additional Attributes overlay for Inquiry processes contain the following fields. Executable Module displays the name of the executable module (EM) that is automatically generated by APPX. APPX derives the file name from the date and time the currently selected inquiry process was added. The name consists of a unique string of eight alphanumeric characters and cannot be changed. If APPX finds it necessary to recreate the EM, the new EM retains the same file name. This field is common to the Additional Attributes overlay for all types of processes. See Process Definition, for more information. Print File Name establishes the name of the file that is used to store the contents of the printed inquiry. If necessary to guarantee uniqueness, APPX may append one or more characters to the value you enter here, or replace one or more of the ending characters. If two or more output/inquiry processes in the same subprocess family are defined with identical Print File values, the processes share a common print file. They print as a single report, with continuous page numbers. If this specification is blank, APPX uses the last Print File that is active within the subprocess family. Cache Priority establishes the likelihood that the process will remain in memory after execution, relative to other processes that the user has also completed executing. A process with a cache priority of 99 is most likely to remain in memory. A process with a cache priority of 1 is least likely to remain in memory. A cache priority of 0 indicates that the process is never cached. The default is 50. This field is common to the Additional Attributes overlay for all types of processes. See Process Definition, for more information. Footer Height indicates the amount of space, in number of rows, to reserve on each page for printing the page footer. APPX uses this value to determine placement of End of Page frames. If blank, APPX does not reserve space for a page footer.
User Cancel OK? contains either 'yes' Default Key Field designates the specific keypath to the PCF that is used in executing the defined inquiry. If blank, the primary key is used. A default keypath that is defined for the invocation of a child process overrides this specification.
Share PCF with Other Users? indicates whether other users can access the designated PCF file when this process is executing. Default is 'yes' Description is incorporated in the message that displays on the screen when the inquiry process is compiling. It is used to communicate with users since it provides a more descriptive and easily understood alternative to Process Name, which is the default if this field is left blank. The Additional Attributes overlay for all types of processes contain this field. See Process Definition, for more information. Report Title defines the text that is used to name the report. This text automatically displays in the standard image for a Start of Page frame which is printed at the top of each page of the inquiry. In Progress Msg provides text for the message that displays to the screen while the report is executing in the foreground. Commit Mode controls the commit mode for a process and can be selected from a drop-down list of available options. Commit Mode determines those points in time when APPX will commit changes made to the tables stored within an RDBMS. It is only applicable in conjunction with an RDBMS; it has no effect with APPXIO. Also, not all File Managers support this feature. Although initially set here for the process, it can be added or overridden by use of predefined field COMMIT MODE. The following options are available: COMPATIBLE. Changes are committed as soon as all locks are freed. This provides maximum compatibility between APPXIO files and RDBMS tables.
AUTOCOMMIT*. APPX will commit each modification as it is made. PCF CYCLE. APPX will commit modifications as each PCF record is processed. END. APPX will only commit modifications at the end of the process family. MANUAL. APPX will not automatically commit changes. You must use the COMMIT statement to do so. Partial-Record I/O is used to specify a field from the PCF file so that instead of operating on the entire PCF record, APPX operates on the designated field only. If the field is a group header, then I/O will be performed on all members of the group. Utilizing partial-record I/O can greatly improve performance when the PCF is a table in an RDBMS. This is especially true when the table contains many columns, but relatively few are being utilized by the process. The scan option is available for field selection. Preferred Form When designing for PDF output, a preferred form can be specified for output and inquiry processes. If specified, it will be used to help tune the image editor session to match the form specifications. The following option is available on the inquiry Additional Attributes overlay. Regenerate Key Entry Frame Option The regenerate key entry frame option allows you to re-create the automatically generated, but modifiable, Key Entry frame that makes inquiry unique and different from output. If you have modified the Key Entry frame for any reason and wish to return to the standard frame, select this option. |
Application Design Manual "Powered by Appx Software"1108 ©2006 By APPX Software, Inc. All Rights Reserved |
or 'no' 
and determines whether or not a user can select the cancel option key to stop the execution of this process. The default is 'yes'. You can conditionally control the user's ability to select the cancel option with statements and the predefined field CANCEL OK. This field is common to the Additional Attributes overlay for all types of processes.